- 4 minutes to read

Release Notes

Monitoring APIs and Web Services

The Nodinite Web Service Monitoring Agent monitors REST APIs, SOAP services, and HTTP endpoints by continuously testing availability, validating responses, measuring performance, and tracking SSL certificate health—automatically generating alerts when endpoints fail or degrade.

On this page: Technical details on endpoint state evaluation, response validation, performance thresholds, and certificate monitoring. For the complete feature overview, see the Web Service Monitoring Agent.

Info

If Nodinite can't check the state of your Web Services, chances are no one else can use them either.

The agent tests your endpoints on configurable intervals (1-60 minutes), validating:

  • HTTP Status Codes – Expected response codes (200, 201, 404, etc.)
  • Response Body – Content validation using RegEx, XPath, or JSON Path expressions
  • Response Times – Performance thresholds for warning and error alerts
  • SSL/TLS Certificates – Expiration dates, certificate chains, cipher suites
  • Authentication – Basic Auth, OAuth2, API Keys, Client Certificates, NTLM

For management actions available on monitored endpoints, see the Managing Web Services page.

State Evaluation for Web Services

Each configured endpoint appears in Nodinite as a Resource within your Monitor Views, organized by Application and Category.

Web Services Monitor View
Example: Web Service endpoints displayed as resources in a Monitor View.

Each Web Service endpoint (Resource) can have one of the following operational states:

State Status Description Actions
Unavailable Resource not accessible Agent cannot reach the endpoint due to network issues, DNS resolution failure, firewall blocking, or SSL/TLS certificate problems Review Prerequisites; check network connectivity; verify DNS resolution; check certificate validity
Error Endpoint failure HTTP status code indicates error (4xx/5xx), response time exceeds error threshold, response body validation failed, or certificate expired View Details; check application logs; verify expected response patterns; review certificate status
Warning Performance degraded Response time exceeds warning threshold but below error threshold, or certificate approaching expiration (within warning period) Monitor performance trends; consider scaling resources; plan certificate renewal
OK Endpoint operational HTTP status code matches expected value, response time within thresholds, response body validation passed (if configured), and certificate valid No action needed; endpoint operating normally

State Evaluation Factors

The agent evaluates multiple factors to determine endpoint health:

  • HTTP Status Code – Validates response matches expected status codes (200, 201, 404, etc.)
  • Response Time – Measures request duration against warning and error thresholds
  • Response Body – Validates content using RegEx, XPath, or JSON Path expressions (if configured)
  • Certificate Health – Monitors SSL/TLS certificate expiration and validity (for HTTPS endpoints)
  • Authentication – Verifies authentication succeeds (Basic Auth, OAuth2, API Keys, Client Certificates)

Tip

Customize state evaluation for individual endpoints using the Expected State feature—useful for maintenance windows or intentionally unavailable test endpoints.

Performance Metrics

Response times are measured for every endpoint test and can be displayed as widgets on the Dashboard.

Web Services Metrics
Example: Metrics graph widget for Web Services on the Nodinite Dashboard.

Configure warning and error thresholds per endpoint to alert when performance degrades. For complete metrics configuration, see Web Services - Metrics.

Supported Endpoint Types

The agent supports comprehensive monitoring across all HTTP-based protocols and patterns:

Protocol Support

  • HTTP/HTTPS – All standard HTTP methods (GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS, TRACE, CONNECT)
  • SOAP 1.1/1.2 – WSDL-based web services with custom message bodies
  • REST APIs – JSON/XML responses with any request parameters
  • Web Applications – Website availability and health checks

Response Validation

  • HTTP Status Codes – Match expected status codes (200, 201, 404, 500, custom ranges)
  • Response Body Validation
    • RegEx – Pattern matching in response content
    • RegEx Match – Extract and validate specific values
    • XPath – Validate XML structure and element values
    • JSON Path – Validate JSON structure and field values

Performance Monitoring

  • Response Time Thresholds
    • Warning level – Alert when response time exceeds warning threshold
    • Error level – Alert when response time exceeds error threshold
  • Metrics Integration – Historical performance tracking and trending

Authentication Methods

  • Client Certificates – Mutual TLS (mTLS) authentication
  • Impersonation – Windows integrated authentication
  • Basic Authentication – Username/password
  • API Keys – Header-based or query parameter authentication
  • OAuth2 – Bearer token authentication with automatic refresh

SSL/TLS Certificate Monitoring

  • Expiration Tracking – Warning and error thresholds for certificate expiry
  • Certificate Chain Validation – Root CA, intermediate, and leaf certificates
  • Certificate Presence Validation – Ensure HTTPS endpoints have valid certificates
  • Graceful Degradation – Continue monitoring even when certificates expire (configurable)

For complete configuration options, see Configuration.

Next Step

Install Web Service Monitoring Agent
Configuration
Managing Web Services

Prerequisites for Web Service Monitoring Agent
Monitoring Certificates
Web Services - Metrics
Monitor Views